Mode: RFC‑S
Trips range 0 - 255
Trip 0 (10.020) to Trip 9 (10.029) store the most recent 10 trips that have occurred where Trip 0 (10.020) is the most recent and Trip 9 (10.029) is the oldest. When a new trip occurs it is written to Trip 0 (10.020) and all the other trips move down the log, with oldest being lost. The date and time when each trip occurs are also stored in the date and time log, i.e. Trip 0 Date (10.041) to Trip 9 Time (10.060). The date and time are taken from Date (06.016) and Time (06.017). Some trips have sub-trip numbers which give more detail about the reason for the trip. If a trip has a sub-trip number its value is stored in the sub-trip log, i.e. Trip 0 Sub-trip Number (10.070) to Trip 9 Sub-trip Number (10.079). If the trip does not have a sub-trip number then zero is stored in the sub-trip log.
Trip categories and priorities
Trips are grouped into the categories given in the table below. A trip can only occur when the drive is not tripped, or if it is already tripped and the new trip has a higher priority than the active trip (i.e. lower priority number). Unless otherwise stated a trip cannot be reset until 1.0s after it has been initiated.
| Priority | Category | Trips | Comments |
| 1 | Internal faults | HF01 - HF28 | These are fatal problems that cannot be reset. All drive features are inactive after any of these trips occur. These trips are not stored in the trip log. |
| 1 | Stored HF trip | Stored HF | This trip cannot be cleared unless 1299 is entered into Parameter mm.000 (mm.000) and a reset is initiated. |
| 2 | Non-resettable trips | Trip numbers 218 to 247, Slot1 HF, Slot2 HF, Slot3 HF or Slot4 HF | These trips cannot be reset. |
| 3 | Volatile memory failure | EEPROM Fail | This can only be reset if Parameter mm.000 (mm.000) is set to 1233 or 1244, or if Load Defaults (11.043) is set to a non-zero value. |
| 4 | Internal 24V power supply | PSU 24V | |
| 5 | Non-volatile media trips | Trip numbers 174, 175 and 177 to 188 | These trips are priority 6 during power-up. |
| 5 | Position feedback interface power supply | Encoder 1 | This trip can override Encoder 2 to Encoder 6 trips. |
| 6 | Trips with extended reset times | OI ac, OI Brake, and OI dc | These trips cannot be reset until 10s after the trip was initiated. |
| 6 | Phase loss and d.c. link power circuit protection | Phase Loss and OHt dc bus | The drive will attempt to stop the motor before tripping if a Phase Loss.000 trip occurs unless this feature has been disabled (see Action On Trip Detection (10.037). The drive will always attempt to stop the motor before tripping if an OHt dc bus occurs. |
| 6 | Standard trips | All other trips |
Internal faults
Trips {HF01} to {HF28} are internal faults that do not have trip numbers. If one of these trips occurs, the main drive processor has detected an irrecoverable error. All drive functions are stopped and the trip message will be displayed on the drive keypad. The error can only be reset by powering the drive down and up again. The table below gives the reasons for internal faults and their corresponding trip.
| Trip | Reason |
| {HF01} | CPU hard fault. |
| {HF02} | CPU memory managment error. |
| {HF03} | CPU bus fault. |
| {HF04} | CPU usage fault. |
| {HF05} | An interrupt has occurred that does not have a defined function (Undefined exception) |
| {HF06} | An interrupt has occurred which is reserved (Reserved exception) |
| {HF07} | Watchdog failure |
| {HF08} | CPU Interrupt crash |
| {HF09} | Free store overflow |
| {HF10} | Parameter routing system error |
| {HF11} | Non-volatile memory comms error |
| {HF12} |
Stack overflow. Sub-trip is shown to indicate which stack: |
| {HF13} | The control hardware is not compatible with the firmware. The sub-trip number gives the actual ID code of the control board hardware. |
| {HF14} | CPU register bank error |
| {HF15} | CPU divide error |
| {HF16} | RTOS error (the background task has returned) |
| {HF17} | The clock supplied to the control board logic is out of specification |
| {HF18} |
The internal flash memory has failed when writing option module parameter data. Sub-trip is shown to indicate which failure: |
| {HF19} | Invalid main application firmware CRC. Reprogramming required. |
| {HF20} | The ASIC is not compatible with the firmware. The sub-trip number displayed is the ASIC version. |
| {HF23} | If this trip occurs please consult the drive supplier. |
| {HF24} | If this trip occurs please consult the drive supplier. |
| {HF25} | If this trip occurs please consult the drive supplier. |
| {HF26} | The control pod is either a UF90A or a UF99A and is fitted to a power stage that is not compatible because it only provided two phase current feedback. If this trip occurs please consult the drive supplier. |
| {HF27} | The internal factory fit I/O module is not compatible with the control board or is not present. The sub-trip shows the hardware identifier given by the module. |
| {HF28} | The internal factory fit position feedback module is not compatible with the control, board. The sub-trip shows the hardware identifier given by the module. |
When the drive is subsequently powered up a Stored HF trip is initiated where the sub-trip number is the number of the HF trip that last occurred. This trip will occur at every power-up until it is reset. The trip can only be reset by first entering 1299 into Parameter mm.000 (mm.000).
Similar trips that can be initiated by the control system or the power system
Trips shown in the table below can be generated either from the drive control system or from the power system. The sub-trip number which is in the form xxyzz is used to identify the source of the trip. The digits xx are 00 for a trip generated by the control system or the number of a power module if generated by the power system. If the drive is not a multi-power module drive then xx will always have a value of 1 indicating the trip is related to the power system. The y digit is used to identify the location of a trip which is generated by a rectifier module connected to a power module. Where the y digit is relevant it will have a value of 1 or more, otherwise it will be 0. The zz digits give the reason for the trip and are defined in each trip description.
| Over Volts | OHt dc bus |
| OI ac | Phase Loss |
| OI Brake | Power Comms |
| PSU | OI Snubber |
| OHt Inverter | Cloning |
| OHt Power | Temp Feedback |
| OHt Control | Power Data |
Braking IGBT
The list below gives conditions that will disable the braking IGBT:
Note that the braking IGBT over-current trip cannot be reset until 10s after it is initiated. This period consists of a 9s period after the trip where the braking IGBT cannot be switched on again and the OI Brake trip is held active and cannot be reset. This 9s period is followed by the normal 1s delay, that is present for other trips, before the trip can be reset. During this 1s period it is possible for the braking IGBT to switch on again. If the conditions are still present that caused the trip then the trip will be initiated again with a further 9s hold-off period etc.
Summary (numerical order)
Descriptions (alphabetic order)
| Trips | Active Rectifier |
|---|---|
| Value | 95 |
| Short description | The active input rectifier has tripped. |
Normally active input rectifier trips give similar trips to the output converter that controls the motor with a suitable sub-trip code to indicate that the trip has been initiated by the rectifier. However it is possible for a fault in the active input rectifier control board to cause other trips that are not intercepted by the main control board. These are indicated by this trip with a sub-trip code that indicates the reason for the trip. The sub-trip code value corresponds to the trips defined by Trip 0 (10.020).
| Trips | An Input 1 Loss |
|---|---|
| Value | 28 |
| Short description | Analog input 1 current loss |
Indicates that a current loss was detected in current mode on Analog Input 1 (Terminal 5, 6). In 4-20mA and 20-4mA modes. loss of input is detected if the current falls below 3mA. See Analog Input 1 Mode (07.007) for further details.
Recommended actions:
| Trips | An Input 2 Loss |
|---|---|
| Value | 29 |
| Short description | Analog input 2 current loss |
Indicates that a current loss was detected in current mode on Analog Input 2 (Terminal 7). In 4-20mA and 20-4mA modes. loss of input is detected if the current falls below 3mA. See Analog Input 2 Mode (07.011) for further details.
Recommended actions:
| Trips | An Output Calib |
|---|---|
| Value | 219 |
| Short description | Analog output calibration failed |
The zero offset calibration of one or both of the analogue outputs has failed. This indicates that the drive hardware has failed, or a voltage has been applied to the output via a low impedance possibly due to a wiring error.
| Sub-trip | Reason |
| 1 | Output 1 failed |
| 2 | Output 2 failed |
Recommended actions:
| Trips | App Menu Changed |
|---|---|
| Value | 217 |
| Short description | Customisation table for an application menu has changed |
The customisation table for an application menu has been changed. The sub-trip indicates which menu has changed:
| Sub-trip | Reason |
| 1 | Menu 18 |
| 2 | Menu 19 |
| 3 | Menu 20 |
If more than one menu has changed the lowest menu has priority. Drive user parameters must be saved to prevent this trip on the next power-up.
Recommended actions:
| Trips | Assist 1 Cycle |
|---|---|
| Value | 121 |
| Short description | Assist soft starter 1 in a Cascade system has started too many times in 1 hour. The Assist needs to cool down. |
This trip is called by the Pump software in the event of Soft Starter Assist 1 starting too many times in an hour as defined by Assist Starts Per Hour (29.120). This trip is only active when Assist Over-cycle Mode (29.121) = Trip and the Pump Control Mode (29.011) = Cascade.
| Trips | Assist 2 Cycle |
|---|---|
| Value | 122 |
| Short description | Assist soft starter 2 in a Cascade system has started too many times in 1 hour. The Assist needs to cool down. |
This trip is called by the Pump software in the event of Soft Starter Assist 2 starting too many times in an hour as defined by Assist Starts Per Hour (29.120). This trip is only active when Assist Over-cycle Mode (29.121) = Trip and the Pump Control Mode (29.011) = Cascade.
| Trips | Assist 3 Cycle |
|---|---|
| Value | 125 |
| Short description | Assist soft starter 3 in a Cascade system has started too many times in 1 hour. The Assist needs to cool down. |
This trip is called by the Pump software in the event of Soft Starter Assist 3 starting too many times in an hour as defined by Assist Starts Per Hour (29.120). This trip is only active when Assist Over-cycle Mode (29.121) = Trip and the Pump Control Mode (29.011) = Cascade.
| Trips | Assist 4 Cycle |
|---|---|
| Value | 126 |
| Short description | Assist soft starter 4 in a Cascade system has started too many times in 1 hour. The Assist needs to cool down. |
This trip is called by the Pump software in the event of Soft Starter Assist 4 starting too many times in an hour as defined by Assist Starts Per Hour (29.120). This trip is only active when Assist Over-cycle Mode (29.121) = Trip and the Pump Control Mode (29.011) = Cascade.
| Trips | Autotune 1 |
|---|---|
| Value | 11 |
| Short description | Position feedback did not change or required speed could not be reached during an autotune |
The drive has tripped during an auto-tune. The cause of the trip can be identified from the sub-trip number.
| Sub-trip | Reason | Recommended actions |
| 1 | The position feedback did not change when position feedback is being used during rotating auto-tune. | Ensure that the motor is free to turn (i.e. mechanical brake is released). Check that the position feedback is selected correctly and operates correctly. |
| 2 | The motor did not reach the required speed during mechanical load measurement. | Ensure that the motor is free to turn and that the static load plus inertia is not too large for the drive to accelerate within the test time. |
| 3 | The required commutation signal edge could not be found during a rotating auto-tune with a Commutation Only position feedback device. | Check that the position feedback signals are connected correctly. |
| 4 | The required movement angle cannot be produced during a minimal movement test. | Reduce the angular movement required. |
| 6 | The phasing offset angle is measured twice during a stationary auto-tune and the results are not within 30o of each other. | If a minimal movement test is being used and excessive motor movement is occurring during the test reduce the required angle movement. Otherwise try and increase the required angle movement. |
| 7 | The motor is moving when a phasing test on enable is selected and the drive is enabled, but the motor is still moving at a speed above the zero speed threshold. | Ensure that the motor is stationary before the drive is enabled. |
| 9 | During the final stage of the minimal movement phasing test with a constrained motor it was not possible to achieve the required movement. | Reduce the angular movement required. |
| 10 | During a stationary autotune saturation test the change of inductance is too small. | Use an alternative test. |
| Trips | Autotune 2 |
|---|---|
| Value | 12 |
| Short description | Position feedback direction incorrect during an autotune |
The drive has tripped during a rotating auto-tune. The cause of the trip can be identified from the associated sub-trip number.
| Sub-trip | Reason | Recommended actions |
| 1 | The position feedback direction is incorrect when position feedback is being used during a rotating auto-tune. | Check motor cable wiring is correct. Check feedback device wiring is correct. Swap any two motor phases to reverse the motor direction. Set either P1 Feedback Reverse (03.056) or Reverse Output Phase Sequence (05.042) to invert the feedback or output phase rotation from the drive. |
| 2 | A SINCOS encoder with comms is being used for position feedback and the comms position is rotating in the opposite direction to the sine wave based position. | Check feedback device wiring is correct. |
| Trips | Autotune 3 |
|---|---|
| Value | 13 |
| Short description | Measured inertia has exceeded the parameter range or commutation signals changed in wrong direction during an autotune |
The drive has tripped during a rotating auto-tune or mechanical load measurement. The cause of the trip can be identified from the associated sub-trip number.
| Sub-trip | Reason | Recommended actions |
| 1 | Measured inertia has exceeded the parameter range during a mechanical load measurement. | |
| 2 | The commutation signals changed in the wrong direction during a rotating auto-tune. | Check motor cable wiring is correct. Check feedback device U, V and W commutation signal wiring is correct. |
| 3 | The mechanical load test has been unable to identify the motor inertia. | Increase the test level. If the test was carried out at standstill repeat the test with the motor rotating within the recommended speed range. |
| Trips | Autotune 4 |
|---|---|
| Value | 14 |
| Short description | Drive encoder U commutation signal fail during an autotune |
A position feedback device with commutation signals is being used (i.e. AB Servo, FD Servo, FR Servo, SC Servo or Commutation Only encoder) and the U commutation signal did not change during a rotating auto-tune.
Recommended actions:
| Trips | Autotune 5 |
|---|---|
| Value | 15 |
| Short description | Drive encoder V commutation signal fail during an autotune |
A position feedback device with commutation signals is being used (i.e. AB Servo, FD Servo, FR Servo, SC Servo or Commutation Only encoder) and the V commutation signal did not change during a rotating auto-tune.
Recommended actions:
| Trips | Autotune 6 |
|---|---|
| Value | 16 |
| Short description | Drive encoder W commutation signal fail during an autotune |
A position feedback device with commutation signals is being used (i.e. AB Servo, FD Servo, FR Servo, SC Servo or Commutation Only encoder) and the W commutation signal did not change during a rotating auto-tune.
Recommended actions:
| Trips | Autotune 7 |
|---|---|
| Value | 17 |
| Short description | Motor number of poles / position feedback resolution set incorrectly |
An Autotune 7 trip is initiated during a rotating auto-tune, if the number of motor poles or the position feedback resolution have been set up incorrectly where position feedback is being used. This trip will not occur if Number Of Motor Poles (05.011) = 6 (i.e. 12 poles).
Recommended actions:
| Trips | Autotune Stopped |
|---|---|
| Value | 18 |
| Short description | Autotune test was stopped before completion |
The drive was prevented from completing an auto-tune, because either the Final drive enable or the Final drive run were removed.
Recommended actions:
| Trips | Bkground Watchdg |
|---|---|
| Value | 123 |
| Short description | The Background task for the Pump software has taken too long to cycle. |
This trip is called by the Pump software in the event of the Background task taking longer than 15s to execute.
| Trips | Brake R Too Hot |
|---|---|
| Value | 19 |
| Short description | Braking resistor thermal protection overload timed out |
This trip indicates that braking resistor overload has timed out. The value in Braking Resistor Thermal Accumulator (10.039) is calculated using Braking Resistor Rated Power (10.030), Braking Resistor Thermal Time Constant (10.031) and Braking Resistor Resistance (10.061). This trip is initiated when Braking Resistor Thermal Accumulator (10.039) reaches 100%.
Recommended actions:
| Trips | CAM |
|---|---|
| Value | 99 |
| Short description | Not applicable |
Not applicable
| Trips | Card Busy |
|---|---|
| Value | 178 |
| Short description | NV media card cannot be accessed as it is being accessed by an option module |
The NV media card is already being accessed via comms, or by an option module, or a file cannot be opened on the drive (i.e. /par/diff file) because the file is already opened via comms.
Recommended actions:
| Trips | Card Data Exists |
|---|---|
| Value | 179 |
| Short description | NV media card file already contains data |
An attempt is being made to write to a file that already exists.
Recommended actions:
| Trips | Card Derivative |
|---|---|
| Value | 188 |
| Short description | Derivative different between the source drive parameter file on the NV media card and the destination drive |
A parameter difference file is being written to the drive, but the value of Drive Derivative (11.028) in the file header is different to the value in the drive. Parameters will be transfered to the target drive but some parameters in the destination drive may have different defaults or ranges, and some parameter may not exist.
Recommended actions:
| Trips | Card Error |
|---|---|
| Value | 182 |
| Short description | Failure to access the NV media card |
Failure to be able to access the card either because there is no card inserted in the drive, or because of a communication failure with the card or because the file system on the card is corrupted.
Recommended actions:
| Trips | Card File Data |
|---|---|
| Value | 187 |
| Short description | Drive mode, required defaults or product type in the parameter file on the NV media card is not compatible with the destination drive |
The drive mode, required defaults or product type in a parameter difference file are not compatible with the drive.
Recommended actions:
| Trips | Card File Error |
|---|---|
| Value | 185 |
| Short description | NV media card header file is incorrect |
The information in the card header (or File /000 in the MCDF folder on an SD card) is out of range. This error can also occur when the file is from a SMART card if the internal file system header information is incorrect (i.e. file type).
Recommended actions:
| Trips | Card Full |
|---|---|
| Value | 184 |
| Short description | NV media card is full |
An attempt has been made to write more data, but the card is full.
Recommended actions:
| Trips | Card No Data |
|---|---|
| Value | 183 |
| Short description | Requested file does not exist on the NV media card |
An attempt has been made to read a file that is not present on the card.
Recommended actions:
| Trips | Card Option |
|---|---|
| Value | 180 |
| Short description | Option modules installed are different between source drive data on the NV media card and destination drive |
A parameter file has been transferred from a NV media card to the drive, but at least one of the option modules are different between source and target drives. This trip does not stop the data transfer but is a warning that the data for the option modules that are different will be set to default values and not the values from the card.
Recommended actions:
| Trips | Card Product |
|---|---|
| Value | 175 |
| Short description | NV media card is from another product and is not compatible |
The NV media card is from another product and is not compatible.
| Trips | Card Rating |
|---|---|
| Value | 186 |
| Short description | Voltage rating different between the source drive parameter file on the NV media card and the destination drive |
A parameter difference file is being written to the drive, but the value of Drive Rated Voltage (11.033) in the file header is different to the value in the drive. Parameters other than those that a rating dependent (i.e. have the RA attribute) will be transferred to the drive although their values maybe limited to be within the range supported by the target drive. Rating dependent parameters will be set to their default value.
Recommended actions:
| Trips | Card Read Only |
|---|---|
| Value | 181 |
| Short description | NV media card is read-only |
An attempt is being made to write to a read-only card or file.
Recommended actions:
| Trips | Card Slot |
|---|---|
| Value | 174 |
| Short description | Communications issue between the drive and option module during an NV media card action |
A failure has occurred in the communications between the drive and an option module when reading or writing data. The sub-trip indicates the option slot.
Recommended actions:
| Trips | Card User Prog |
|---|---|
| Value | 177 |
| Short description | Onboard user program is write-only or does not exist, and cannot be transferred to an NV media card |
An attempt has been made to transfer an onboard user program from the drive to the card but this is not possible due to one of the following reasons.
| Trips | Clean Over-cycle |
|---|---|
| Value | 120 |
| Short description | The cleaning cycle has automatically started too many times in 1 hour. Check the pump inlet to see if it has become blocked. |
This trip is called by the Pump software in the event of the pump cleaning cycle running too many times as defined by Clean Per Hour Limit (29.100). This trip is only active if Clean Per Hour Limit Mode (29.101) = Trip.
| Trips | Cloning |
|---|---|
| Value | 102 |
| Short description | Failure of the cloning function |
If an attempt is made to use the cloning system to back-up the drive and option modules (parameter mm.000 values from 40001 to 40999) or restore the drive and option modules (parameter mm.000 values from 60001 to 60999) and the action fails then a "Cloning" trip is initiated. The sub-trip value indicates the reason for the trip.
| Sub-trip | Reason |
| 1 | The option module in Slot 1 has indicated that it will either back-up or restore its data to/from an SD card, but has failed to respond correctly and the system has timed out. |
| 2 | As 1, but for Option Slot 2. |
| 3 | As 1, but for Option Slot 3. |
| 4 | As 1, but for Option Slot 4. |
| 5 | Back-up folders exist or cannot be created when a back-up is initiated. |
| 6 | The required back-up folders do not exist when a restore is initiated. |
| Trips | Configuration |
|---|---|
| Value | 111 |
| Short description | Number of power modules or rectifiers installed is different from the number expected |
The Number Of Power Modules Detected (11.071) is different from the number expected. The sub-trip value indicates the number of power modules expected.
Recommended actions:
This trip is also initiated if the number of external rectifiers connected to each power module is less than the number defined by Number Of Rectifiers Expected (11.096). If this is the reason for the trip the sub-trip is 10x where x is the number of external rectifiers that should be connected.
Recommended actions:
| Trips | Control Word |
|---|---|
| Value | 35 |
| Short description | Trip initiated from the Control Word |
This trip is initiated by setting bit 12 on the control word in Control Word (06.042) when the control word is enabled (Control Word Enable (06.043) = On).
Recommended actions:
| Trips | Ctrl Wrd Watchdg |
|---|---|
| Value | 124 |
| Short description | The pump drive is operating in control word mode and the control word watchdog bit hasn't been serviced. |
This trip is called by the Pump software in the event of Pump Control Word 1 (29.151) watchdog bit15 not being toggled for Pump Control Word Watchdog Time (29.150) seconds. This protects the system in the event that a HMI or PLC that is controlling the system becomes disconnected. This is only used when Pump Control Mode (29.011) = Multi-leader.
| Trips | Current Offset |
|---|---|
| Value | 225 |
| Short description | Current feedback offset error |
The current feedback offset is too large to be trimmed correctly. The current feedback offset is always measured at power up before the drive is enabled. In motor control modes the current feedback offset is also measured whenever the drive is not active such that no current should be flowing in the output. In regen mode the current feedback offset is measured when the drive comes out of the under voltage state.
The sub-trip relates to the output phase for which the offset error has been detected.
| Sub-trip | Reason |
| 1 | U phase |
| 2 | V phase |
| 3 | W phase |
Recommended actions:
| Trips | Data Changing |
|---|---|
| Value | 97 |
| Short description | Drive parameter data is changing and the drive has been commanded to enable |
A user action or a file system write is active that is changing the drive parameters and the drive has become active, i.e. Drive Active (10.002) = 1. The user actions that change drive parameters are loading defaults, changing drive mode, or transferring data from an NV memory card or a position feedback device to the drive. The file system actions that will cause this trip to be initiated if the drive is enabled during the transfer are writing a parameter or macro file to the drive, or transferring a derivative or user program to the drive. It should be noted that none of these actions can be started if the drive is active, and so the trip only occurs if the action is started and then the drive is enabled.
Recommended actions:
| Trips | Derivative ID |
|---|---|
| Value | 247 |
| Short description | Derivative identification error |
There is a problem with the identifier associated with derivative image which customises the drive. The reason for the trip is given by the sub-trip as follows.
| Sub-trip | Reason |
| 1 | There should be a derivative image in the product but this has been erased. |
| 2 | The identifier is out of range. |
| 3 | The derivative image has been changed. |
| Trips | Derivative Image |
|---|---|
| Value | 248 |
| Short description | Derivative product image error |
An error has been detected in the derivative product image. The sub-trip indicated the reason for the trip.
| Sub-trip | Reason | Comments |
| 1 | Divide by zero | |
| 2 | Undefined trip | |
| 3 | Attempted fast parameter access set-up with non-existent parameter | |
| 4 | Attempted access to non-existent parameter | Check that the SI-Ethernet firmware is a minimum of V01.07.03.03. Versions of SI-Ethernet firmware ealier than this can cause this trip when F600 Pump Control Mode (29.011) = Multi-leader. |
| 5 | Attempted write to read-only parameter | |
| 6 | Attempted and over-range write | |
| 7 | Attempted read from write-only parameter | |
| 30 | The image has failed because either its CRC is incorrect, or there are less than 6 bytes in the image or the image header version is less than 5. | Occurs when the drive powers-up or the image is programmed. The image tasks will not run. |
| 31 | The image requires more RAM for heap and stack than can be provided by the drive. | As 30. |
| 32 | The image requires an OS function call that is higher than the maximum allowed. | As 30. |
| 40 | The timed task has not completed in time and has been suspended. | |
| 41 | Undefined function called, i.e. a function in the host system vector table that has not been assigned. | As 40. |
| 51 | Core menu customisation table CRC check failed | As 30. |
| 52 | Customisable menu table CRC check failed | As 30. |
| 53 | Customisable menu table changed | Occurs when the drive powers-up or the image is programmed and the table has changed. Defaults are loaded for the derivative menu and the trip will keep occurring until drive parameters are saved. |
| 61 | The option module fitted in slot 1 is not allowed with the derivative image. | As 30. |
| 62 | The option module fitted in slot 2 is not allowed with the derivative image. | As 30. |
| 63 | The option module fitted in slot 3 is not allowed with the derivative image. | As 30. |
| 64 | The option module fitted in slot 4 is not allowed with the derivative image. | As 30. |
| 70 | An option module that is required by the derivative image is not fitted in any slot. | As 30. |
| 71 | An option module specifically required to be fitted in slot 1 not present. | As 30. |
| 72 | An option module specifically required to be fitted in slot 2 not present. | As 30. |
| 73 | An option module specifically required to be fitted in slot 3 not present. | As 30. |
| 74 | An option module specifically required to be fitted in slot 4 not present. | As 30. |
| 80 | *Image is not compatible with the control board | Initiated from within the image code. |
| 81 | *Image is not compatible with the control board serial number | As 80. |
Recommended actions:
| Trips | Destination |
|---|---|
| Value | 199 |
| Short description | The destination of two or more functions are writing to the same parameter |
This trip indicated that destination output parameters of two or more logic functions (Menus 05, 07, 08, 09, 12 or 14) within the drive are writing to the same parameter.
Recommended actions:
| Trips | Drive Size |
|---|---|
| Value | 224 |
| Short description | Unrecognized drive size/rating |
This trip indicates that the control PCB has not recognized the drive size of the power circuit to which it is connected.
Recommended actions:
| Trips | Dry Well |
|---|---|
| Value | 115 |
| Short description | The dry well detection system has detected a dry well. Please ensure there is sufficient water in the well and that the pump inlet pipes are connected properly. |
This trip is called by the Pump software in the event of a Dry Well Low Load detection when Dry Well Low Load Mode (29.059) = Trip.
| Trips | EEPROM Fail |
|---|---|
| Value | 31 |
| Short description | Non-volatile memory issue detected causing default parameter values to be loaded |
EEPROM Fail trip indicates that default parameters have been loaded because of the reasons given below.
| Sub-trip | Reason |
| 1 | The most significant digit of the internal parameter database version number has changed. |
| 2 | The CRC's applied to the parameter data stored in internal non-volatile memory indicate that a valid set of parameters cannot be loaded. |
| 3 | The drive mode restored from internal non-volatile memory is outside the allowed range for the product or the derivative image does not allow the previous drive mode. |
| 4 | The drive derivative image has been changed and it has changed the customisation of the drive core menus. |
| 5 | The power stage hardware has been changed and it has changed the customisation of the drive core menus. |
| 6 | The internal I/O hardware has been changed and it has changed the customisation of the drive core menus. |
| 7 | The position feedback interface hardware has been changed and it has changed the customisation of the drive core menus. |
| 8 | The control board hardware has been changed and it has changed the customisation of the drive core menus. |
| 9 | The checksum on the non-parameter area of the EEPROM has failed. |
The drive holds two banks of user save parameters and two banks of power down save parameters in non-volatile memory. If the last bank of either set of parameters that was saved is corrupted a User Save or Power Down Save trip is produced. If one of these trips occurs the parameters values that were last saved successfully are used. It can take some time to save parameters when requested by the user and if the power is removed from the drive during this process it is possible to corrupt the data in the non-volatile memory. The Power Down Save trip can occur if the d.c. bus is discharged too quickly after the supply has been removed, for example with the use of external discharge resistors.
If both banks of user save parameters or both banks of power down save parameters are corrupted or one of the other conditions given in the table above occurs an EEPROM Fail.2 trip is produced. If this trip occurs it is not possible to use the data that has been saved previously, and so the drive will be in lowest allowed drive mode with default parameters. The trip can only be reset if Parameter mm.000 (mm.000) is set to 10, 11, 1233 or 1244 or if Load Defaults (11.043) is set to a non-zero value.
Recommended actions:
| Trips | Encoder 1 |
|---|---|
| Value | 189 |
| Short description | Drive position feedback interface power supply overload |
Not applicable
| Trips | Encoder 2 |
|---|---|
| Value | 190 |
| Short description | Wire break between the drive and the position feedback device |
Not applicable
| Trips | Encoder 3 |
|---|---|
| Value | 191 |
| Short description | Incorrect position feedback phase offset angle detected while running |
Not applicable
| Trips | Encoder 4 |
|---|---|
| Value | 192 |
| Short description | Encoder communications has timed out |
Not applicable
| Trips | Encoder 5 |
|---|---|
| Value | 193 |
| Short description | Encoder communications checksum or CRC error |
Not applicable
| Trips | Encoder 6 |
|---|---|
| Value | 194 |
| Short description | Encoder has indicated an error |
Not applicable
| Trips | Encoder 7 |
|---|---|
| Value | 195 |
| Short description | Set-up parameters for the position feedback device have changed |
Not applicable
| Trips | Encoder 8 |
|---|---|
| Value | 196 |
| Short description | Encoder communications time exceeds 250us |
Not applicable
| Trips | Encoder 9 |
|---|---|
| Value | 197 |
| Short description | Selected motor control feedback source does not contain position feedback category option module |
Not applicable
| Trips | Encoder 11 |
|---|---|
| Value | 161 |
| Short description | Selected device type is not supported by the drive |
This trip indicates that the drive hardware does not support the selected position feedback device type (see Control Board Identifier (11.067) for more information on control board capabilities).
| Sub-trip | Reason |
| 1 | Drive position feedback interface 1 |
| 2 | Drive position feedback interface 2 |
Recommended actions:
| Trips | Encoder 12 |
|---|---|
| Value | 162 |
| Short description | Encoder could not be identified during auto-configuration |
Not applicable
| Trips | Encoder 13 |
|---|---|
| Value | 163 |
| Short description | Data read from the encoder is out of range during auto-configuration |
Not applicable
| Trips | Encoder 14 |
|---|---|
| Value | 164 |
| Short description | Data in the additional configuration parameter is out of range |
Not applicable
| Trips | Ext Pump Fault |
|---|---|
| Value | 116 |
| Short description | The external pump fault input has been triggered. Please check the external pump fault trigger circuit. |
This trip is called by the Pump software in the event of the External Pump Fault Input (29.085) being set to On(1).
| Trips | External Trip |
|---|---|
| Value | 6 |
| Short description | External Trip has occurred |
External trip is initiated as shown in the table below.
| Sub-trip | Reason |
| 1 | External Trip Mode (08.010) = 1 or 3 and Safe Torque Off Input 1 is low |
| 2 | External Trip Mode (08.010) = 2 or 3 and Safe Torque Off Input 2 is low |
| 3 | External Trip (10.032) = 1 |
Recommended actions:
| Trips | I/O Overload |
|---|---|
| Value | 26 |
| Short description | Digital output overload |
This trip indicates that the total current drawn from the 24V user supply or from the digital output has exceeded the limit. A trip is initiated if one or more of the following conditions:
Recommended actions:
| Trips | Inductance |
|---|---|
| Value | 8 |
| Short description | Inductance measurement out of range or motor saturation not detected |
This trip occurs in RFC-S mode when the drive has detected that the motor inductances are not suitable for the operation being attempted. The trip is either caused because the ratio or difference between Ld and Lq is too small or because the saturation characteristic of the motor cannot be measured.
If the inductance ratio or difference is too small this is because one of the following conditions is true:
(No-load Lq (05.072)- Ld (05.024)) / Ld (05.024) < 0.2
(No-load Lq (05.072) - Ld (05.024)) < (K / Full Scale Current Kc (11.061)) H
where:
| Drive Rated Voltage (11.033) | K |
| 200V | 0.0073 |
| 400V | 0.0146 |
| 575V | 0.0174 |
| 690V | 0.0209 |
If the saturation characteristic of the motor cannot be measured this is because when the flux in the motor is changed the measured value of Ld does not change sufficiently due to saturation to be measured. When half of Rated Current (05.007) is applied in the d axis of the motor in each direction the inductance must change by at least (K / (2 x Full Scale Current Kc (11.061))) H.
The specific reasons for each of the sub-trips are given in the table below.
| Sub-trip | Reason |
| 1 | The inductance ratio or difference is too small when the drive has been started in sensorless mode. |
| 2 | The saturation characteristic of the motor cannot be measured when the drive has been started in sensorless mode. |
| 3 | The inductance ratio or difference is too small when an attempt is made to determine the location of the motor flux during a stationary auto-tune in RFC-S mode. This trip is also produced when the inductance ratio or inductance difference is too small when carrying out a phasing test on starting in RFC-S mode. If position feedback is being used the measured value for Position Feedback Phase Angle (03.025) may not be reliable. Also the measured values of Ld (05.024) and No-load Lq (05.072) may not correspond to the d and q axis respectively. |
| 4 | The direction of the flux in the motor is detected by the change of inductance with different currents. This trip is initiated if the change cannot be detected when an attempt is made to perform a stationary auto-tune when position feedback is being used, or to perform a phasing test on starting in RFC-S mode. |
| Trips | Inductor Too Hot |
|---|---|
| Value | 93 |
| Short description | Not applicable |
Not applicable
| Trips | Inter-connect |
|---|---|
| Value | 103 |
| Short description | Multi-module drive interconnection cable error |
Multi-power module drive interconnection cable error. The sub-trip "xx000" indicates which power module has detected the fault where xx is the power module number. This trip is also initiated if the number of modules present changes from the number of modules detected at power-up. In this case the sub-trip is the number of modules that are still communicating correctly.
| Trips | Island |
|---|---|
| Value | 160 |
| Short description | Not applicable |
Not applicable
| Trips | Keypad Mode |
|---|---|
| Value | 34 |
| Short description | Keypad has been removed when the drive is in keypad mode |
Not applicable
| Trips | Line Sync |
|---|---|
| Value | 39 |
| Short description | Not applicable |
Not applicable
| Trips | Low Load |
|---|---|
| Value | 38 |
| Short description | The load on the drive has fallen below the Low Load Detection Level |
This trip is initiated if the low load detector is set up to produce a trip on low load detection and this condition occurs. See Enable Trip On Low Load (04.029).
| Trips | Motor Over Temp |
|---|---|
| Value | 118 |
| Short description | The motor thermal protection device has activated and the pump motor is too hot. |
This trip is called by the Pump software in the event of the Motor Thermal Protection Input (29.086) being set to Off(0) when Motor Thermal Protection Enable (29.087) = On(1).
| Trips | Motor Too Hot |
|---|---|
| Value | 20 |
| Short description | Motor thermal protection overload timed out |
This trip indicates a motor thermal overload based on the Rated Current (05.007) and Motor Thermal Time Constant 1 (04.015). Motor Protection Accumulator (04.019) displays the motor temperature as a percentage of the maximum value. The drive will trip on Motor Too Hot when Motor Protection Accumulator (04.019) gets to 100%.
Recommended actions:
| Trips | Name Plate |
|---|---|
| Value | 176 |
| Short description | Electronic nameplate transfer has failed |
This trip is initiated if there is a problem detected when an electronic name plate transfer from the motor to the drive is initiated. The reasons for the trip are given below:
| Sub-trip | Reason | Details |
| 1 | A communication error with the encoder has been detected. | It is unlikely that this sub-trip will occur as most encoder errors will cause an encoder trip. It is possible that incorrect data in the nameplate could cause this trip, and so the nameplate data should be verified. |
| 2 | A data error has been detected in the nameplate. This is either because the number of entries is out of range, i.e. less than 1 or greater than 168, or the calculated CRC does not match the CRC from the nameplate. | Either there is no valid nameplate in the position feedback device or there is a data error in the nameplate area. |
| 3 | The exchange with the encoder has timed out. | If the encoder is connected to a drive interface, then this occurs because the encoder is not connected to the drive or is not initialised. If the encoder is connected to an option module interface, then this occurs because the position feedback interface (i.e. P1 or P2) is not present on the option module, or a suitable position feedback device is not selected, or because no device is connected, or it is not initialised. |
| Trips | Network Loss |
|---|---|
| Value | 119 |
| Short description | A multi-leader drive has detected a loss of Ethernet RTMoE communications. Please check the Ethernet network connections and setup. |
This trip is called by the Pump software in the event of a loss Ethernet RTMoE comms from this drive to it's Leader in a Multi-leader system. This trip is enabled when Multi-leader Network Loss Mode (29.133) = Trip. The trip may be disabled by setting Multi-leader Network Loss Mode (29.133) = Run Single Pump where instead of tripping the drive will run as a single pump, independent of the Leader.
| Trips | No Encoder Found |
|---|---|
| Value | 167 |
| Short description | An encoder could not be identified during auto-discovery |
An encoder supported by the auto-discovery process has not been found (see Discovery in P1 Device Type (03.038) for more information on this process). Please ensure that a supported device is connected to the drive P1 interface and the required P1 Supply Voltage (03.036) is set for the device. The sub-trip will always be 1 as only the P1 interface supports auto-discovery.
Recommended actions:
| Trips | None |
|---|---|
| Value | 0 |
| Short description | No trip |
No trip has been stored in this position in the trip log.
| Trips | OHt Brake |
|---|---|
| Value | 101 |
| Short description | Braking IGBT over-temperature |
This trip indicates that braking IGBT over-temperature has been detected based on firmware thermal model.
Recommended actions:
| Trips | OHt Control |
|---|---|
| Value | 23 |
| Short description | Control stage over temperature |
This trip indicates that a control stage over-temperature has been detected. From the sub-trip "xxyzz", the cause of the trip can be identified as follows:
| Source | xx | y | zz |
| Control system | 00 | 0 or 1* | 01: Control board thermistor 1 |
| Control system | 00 | 0 or 1* | 02: Control board thermistor 2 |
| Control system | 00 | 0 | 03: I/O board thermistor (or brake resistor thermistor) |
*1 indicates the trip has been initiated by the active input rectifier control if present.
Recommended actions:
| Trips | OHt dc bus |
|---|---|
| Value | 27 |
| Short description | DC bus over temperature based on thermal model |
This trip indicates a DC bus component over temperature based on a firmware thermal model. The drive includes a thermal protection system to protect the DC bus components within the drive. This includes the effects of the output current and DC bus ripple. The estimated temperature is displayed as a percentage of the trip level in Percentage Of d.c. Link Thermal Trip Level (07.035). If this parameter reaches 100% then an OHt dc bus trip with sub-trip 200 is initiated. The drive will attempt to stop the motor before tripping. If the motor does not stop in 10 seconds then the drive trips immediately.
| Source | xx | y | zz |
| Control system | 00 | 2 | 00: D.c. link thermal model gives {OHt dc bus} trip with sub-trip 0. |
It is also possible in a multi-power module system for d.c. link over-temperature to be detected from within the power stage. From this source the estimated temperature as a percentage of trip is not available and the trip is indicated as follows:
| Source | xx | y | zz |
| Power system | 01 | 0 | 00: Power stage gives {OHt dc bus} trip with sub-trip 0. |
Recommended actions:
| Trips | OHt Inverter |
|---|---|
| Value | 21 |
| Short description | Inverter over temperature based on thermal model |
This trip indicates that an IGBT junction over-temperature has been detected based on a firmware thermal model. The sub-trip indicates which model has initiated the trip in the form xxyzz as given below.
| Source | xx | y | zz |
| Control system | 00 | 1 | 00: Inverter thermal model |
| Control system | 00 | 3 | 00: Braking IGBT thermal model |
| Control system | 00 | 4 | 00: Rectifier thermal model or active input converter if present. |
Recommended actions with sub-trip 100:
Recommended actions with sub-trip 300:
Recommended actions with sub-trip 400:
| Trips | OHt Power |
|---|---|
| Value | 22 |
| Short description | Power stage over temperature |
This trip indicates that a power stage over-temperature has been detected. The sub-trip "xxyzz" indicates which thermistor is indicating the over-temperature. The thermistor numbering is different for a single module type drive (i.e. no parallel board fitted) and a multi-module type drive (i.e. parallel board fitted with one or more power modules) as shown below:
Single module type drive:
| Source | xx | y | zz |
| Power system | 01 | 0 | zz: Thermistor location defined by zz in the power board |
| Power system | 01 | Rectifier number | Drive with thyristor rectifier input. zz: Thermistor location defined by zz in the rectifier |
| Power System | 01 | 1 | Drive with active input converter. zz: Thermistor location defined by zz in the input converter |
Multi-module type system:
| Source | xx | y | zz |
| Power system | Power module number | 0 | 01: U phase power device |
| Power System | Power module number | 0 | 02: V phase power device |
| Power system | Power module number | 0 | 03: W phase power device |
| Power system | Power module number | 0 | 04: Rectifier |
| Power system | Power module number | 0 | 05: General power system |
| Powersystem | Power module number | 0 | 00: Braking IGBT |
Note that the power module that has caused the trip cannot be identified except for the braking IGBT temperature measurement.
Recommended actions:
| Trips | OI ac |
|---|---|
| Value | 3 |
| Short description | Instantaneous output over current detected |
This trip indicates that the instantaneous drive output current has exceeded the drive over current threshold.
| Source | xx | y | zz |
| Control system | 00 | 0 | 00 |
| Active input converter | 00 | 1 | 00 |
| Power system | Power module number | 0 | 00 |
The over current threshold is the maximum current the drive can measure and is defined by Full Scale Current Kc (11.061).
Recommended actions:
| Trips | OI Brake |
|---|---|
| Value | 4 |
| Short description | Braking IGBT over current detected or short circuit protection for the braking IGBT activated |
This trip indicates that an over-current has been detected in braking IGBT or braking IGBT protection has been activated. The braking IGBT over-current trip is detected within the power system. If the drive is a single module drive then there is no sub-trip. If the drive is a multi-power module drive the following sub-trip is used to indicate the source of the trip.
| Source | xx | y | zz |
| Power system | Power module number | 0 | 00: Braking IGBT instantaneous over-current trip |
Recommended actions:
| Trips | OI dc |
|---|---|
| Value | 109 |
| Short description | Drive output stage short circuit detected |
This trip indicates that the short circuit protection for the drive output stage has been activated. The table below shows where the trip has been detected.
| Source | xx | y | zz |
| Control system | 00 | 0 | 00 |
| Power system | Power module number | 0 | 00 |
Recommended actions:
| Trips | OI Snubber |
|---|---|
| Value | 92 |
| Short description | Over-current condition detected in the rectifier snubber circuit |
This trip indicates that an over-current condition has been detected in the rectifier snubbing circuit, The exact cause of the trip can be identified by the sub-trip number.
| Source | xx | y | zz |
| Power system | 01 | Rectifier number* | 00: Rectifier snubber over-current trip detected. |
*For a parallel power-module system the rectifier number will be one as it is not possible to determine which rectifier has detected the fault.
Recommended actions:
| Trips | Option Disable |
|---|---|
| Value | 215 |
| Short description | Option module did not acknowledge during drive mode changeover |
During drive mode changeover option modules must acknowledge that they have stopped accessing the communications system between the option slots and the drive. If an option module does not do this in the allowed time then this trip is produced.
Recommended actions:
| Trips | Out Phase Loss |
|---|---|
| Value | 98 |
| Short description | Phase loss been detected at the output of the drive |
This trip indicates that phase loss has been detected at the drive output.
| Sub-trip | Reason |
| 1 | U phase output not connected when drive is enabled* |
| 2 | V phase output not connected when drive is enabled* |
| 3 | W phase output not connected when drive is enabled* |
| 4 | Output phase loss detected when the drive is running |
| 5 | U phase lower IGBT failure detection on drive enable |
| 6 | V phase lower IGBT failure detection on drive enable |
| 7 | W phase lower IGBT failure detection on drive enable |
*These sub-trips could also indicate that the upper IGBT has failed in the indicated phase.
Recommended actions:
| Trips | Over Speed |
|---|---|
| Value | 7 |
| Short description | Motor over speed has occurred |
In open-loop mode, if the Output Frequency (05.001) exceeds the threshold set in Over Speed Threshold (03.008) in either direction, an Over Speed trip is produced. In RFC-A and RFC-S modes, if the Speed Feedback (03.002) exceeds the threshold set in Over Speed Threshold (03.008) in either direction, an Over Speed trip is produced. If Over Speed Threshold (03.008) is set to 0.0 the threshold is then equal to 1.2 x the value set in Maximum Reference Clamp (01.006).
Recommended action:
The above description relates to a standard over speed trip, however in RFC-S mode it is possible to produce an Overspeed trip with sub-trip 1. This is caused if the speed is allowed to exceed the safe level in RFC-S mode with flux weakening. See Enable High Speed Mode (05.022) for details.
| Trips | Over Volts |
|---|---|
| Value | 2 |
| Short description | DC bus voltage has exceeded the peak level or maximum continuous level for a period of time |
This trip indicates that the DC bus voltage has exceeded VM_DC_VOLTAGE[MAX], or the DC bus voltage has been higher than the maximum continuous voltage level for a period of time. The trip threshold varies depending on voltage rating of the drive as shown below.
| Voltage rating | VM_DC_VOLTAGE[MAX] | Maximum continuous voltage level |
| 200 | 415 | 410 |
| 400 | 830 | 815 |
| 575 | 990 | 970 |
| 690 | 1190 | 1175 |
The exact cause of the trip can be identified by the sub-trip number.
| Source | xx | y | zz |
| Control system | 00 | 0 | 01: Instantaneous trip when the d.c. link voltage exceeds VM_DC_VOLTAGE[MAX]. |
| Control system | 00 | 0 | 02: Time delayed trip indicating that the d.c. link voltage has been above the maximum continuous voltage level for a period of time. |
| Active input converter | 00 | 1 | 00: Instantaneous trip when the d.c. link voltage exceeds VM_DC_VOLTAGE[MAX]. |
Recommended actions:
| Trips | Over-cycle |
|---|---|
| Value | 117 |
| Short description | The pump drive has been through the wake / sleep cycle too many times in 1 hour. |
This trip is called by the Pump software in the event of the over-cycle protection scheme counting too may starts per hour when Over-cycle Mode (29.127) = Trip.
| Trips | Phase Imbalance |
|---|---|
| Value | 104 |
| Short description | Phase imbalance has been detected (Regen mode only) |
The level of supply phase imbalance has cause the negative phase sequence components to exceed the threshold defined by Phase Imbalance Threshold .
| Trips | Phase Loss |
|---|---|
| Value | 32 |
| Short description | Phase loss detected at the supply input to the drive |
This trip indicates that the drive has detected an input phase loss or large supply imbalance. Phase loss can be detected directly from the supply where the drive has a thyristor base charge system (Frame size 7 and above). If phase loss is detected using this method the drive trips immediately and the xx part of the sub-trip is set to 01. In all sizes of drive phase loss is also detected by monitoring the ripple in the d.c. link voltage in which case the drive attempts to stop the drive before tripping unless bit 2 of Action On Trip Detection (10.037) is set to one. When phase loss is detected by monitoring the ripple in the d.c. link voltage the xx part of the sub-trip is zero.
| Source | xx | y | zz |
| Control system | 00 | 0 | 00: Phase loss detected from d.c. link ripple |
| Power system (1) | 01 | Rectifier number (2) | 00: Phase loss detected directly from the supply |
(1) Input phase loss detection can be disabled when the drive required to operate from the DC supply or from a single phase supply in Input Phase Loss Detection Mode (06.047).
(2) For a parallel power-module system the rectifier number will be one as it is not possible to determine which rectifier has detected the fault.
This trip does not occur in regen mode.
Recommended actions:
| Trips | Phasing Error |
|---|---|
| Value | 198 |
| Short description | Incorrect phase offset angle in RFC-S mode |
If position feedback is being used this trip indicates that the phase offset angle in Position Feedback Phase Angle (03.025) is incorrect and that the drive is unable to control the motor correctly.
Recommended actions:
If sensorless control is being used this indicates that significant instability has occurred and the motor has accelerated without control. For low saliency motors (Active Saliency Torque Mode (05.066) < 2) this operates in the same way as when position feedback is used, based on the speed of the motor and the voltages applied. For high saliency motors (Active Saliency Torque Mode (05.066) = 2) this type of detection cannot be used and the over-speed trip should be used instead. However this trip is used for high saliency motors when low speed control using current injection is being used (Active Saliency Torque Mode (05.066) = 2) and control is lost because the motor has become non-salient. The saliency of most permanent magnet motors reduces with load, and so Low Speed Sensorless Mode Current (05.071) must be set to a level to limit the current so that the motor remains salient enough for control.
Recommended actions:
| Trips | PID Feedbk High |
|---|---|
| Value | 113 |
| Short description | The main PID1 process feedback is greater than the PID feedback high threshold. |
This trip is called by the Pump software in the event of the main process PID1 feedback going above the PID Feedback High Trip Threshold (29.041). This trip can be disabled by setting PID Feedback High Trip Threshold (29.041) = 0.
| Trips | PID Feedbk Loss |
|---|---|
| Value | 112 |
| Short description | The main process PID1 4-20mA transducer isn't providing the minimum current of 4mA. Check the connections to Analog input1. |
This trip is called by the Pump software in the event of a loss of main process PID1 feedback when PID Feedback Loss Action (29.048) = Trip and Analog Input 1 Current Loop Loss (07.028) = On(1).
| Trips | PID Feedbk Low |
|---|---|
| Value | 114 |
| Short description | The main PID1 process feedback is less than the PID feedback low threshold. |
This trip is called by the Pump software in the event of the main process PID1 feedback going below the PID Feedback Low Threshold (29.044). This trip can be disabled by setting PID Feedback Low Mode (29.043) to Disabled.
| Trips | Power Comms |
|---|---|
| Value | 90 |
| Short description | Communications problem within the power system of the drive |
A Power Comms trip indicates a communications problem within the power system of the drive. The reason for the trip can be identified by the sub-trip number.
| Type of drive | xx | y | zz |
| Single power module system | 01 | Rectifier number* | 00: Excessive communications errors detected by the rectifier module. |
| Drive with active rectifier | 01 | 0 | 00: Communications with the active rectifier control has been lost. XX: Where XX > 00 indicates an internal (HF) fault in the control system for the active input converter if present. See Trip 0 (10.020). |
| Drive with active rectifier | 01 | 1 | 00: The active rectifier control board is in bootloader mode. |
*For a parallel power-module system the rectifier number will be one as it is not possible to determine which rectifier has detected the fault.
Recommended actions:
| Trips | Power Data |
|---|---|
| Value | 220 |
| Short description | Power system configuration/rating data error |
This trip can be generated either from the drive control system or from the power system.
This trip is produced if there is an error in the configuration data stored in the power system. If the source of the trip is the control system then the trip related to the table that is uploaded from the power system at power-up.
| Source | xx | y | zz |
| Control system | 00 | 0 | 02: There is no data table to be uploaded to the control board. |
| Control system | 00 | 0 | 03: The power system data table is bigger than the space available in the control pod to store it. |
| Control system | 00 | 0 | 04: The size of the table given in the table is incorrect |
| Control system | 00 | 0 | 05: Table CRC error. |
| Control system | 00 | 0 | 06: The version number of the generator software that produced the table is too low, i.e. a table from a newer generator is required that includes features that have been added to the table that may not be present. |
| Control system | 00 | 0 | 07: The power board data table does not match the power board hardware identifier. |
| Power system | 01 | 0 | 00: The power data table used internally by the power module has an error. (For a multi-power module drive this indicates any error with the code tables in the power system.) |
| Power system | 01 | 0 | 01: The power data table that should be uploaded to the control system on power up has an error. |
| Power system | 01 | 0 | 02: The power data table used internally by the power module does not match the hardware identification of the power module. |
Recommended actions:
| Trips | Power Down Save |
|---|---|
| Value | 37 |
| Short description | Error detected in the power down save parameter data saved in non-volatile memory |
This trip indicates that an error has been detected in the power down save parameters stored in non-volatile memory.
On drives other than Digitax HD, Power down save parameters are saved when the drive enters the under voltage state after the supply has been removed. This trip can occur if the d.c. bus is discharged too quickly after the supply is removed as the drive then doesn't have enough time to save these parameters before the internal power supply in the drive shuts down resulting in corruption of the saved data.
Recommended actions:
| Trips | PSU |
|---|---|
| Value | 5 |
| Short description | Internal power supply fault |
This trip indicates that one or more internal power supply rails are outside limits or overloaded.
| Source | xx | Y | zz |
| Control system | 00 | 0 | 00: Internal power supply overload. |
| Active input converter | 00 | 1 | 00: Internal power supply overload. |
| Power system | Power module number | Rectifier number* | 00: Rectifier internal power supply overload. |
*For a parallel power-module system the rectifier number will be zero as it is not possible to determine which rectifier has detected the fault.
Recommended actions:
| Trips | PSU 24V |
|---|---|
| Value | 9 |
| Short description | 24V internal power supply overload |
The total user load of the drive and option modules has exceeded the internal 24V power supply limit. The user load consists of the following:
If the sub-trip code is 100, this indicates that this fault has been detected by the control board for the active input converter if present.
Recommended actions:
| Trips | Rating Mismatch |
|---|---|
| Value | 223 |
| Short description | Voltage or current rating mismatch between power modules in a multi-module drive |
This trip indicates that there is a voltage rating or current rating mismatch in a multi-module drive system. This trip is only applicable to modular drives that are connected in parallel. A mixture of power modules with different voltage or current ratings within the same multi-module drive system is not allowed and will cause a Rating Mismatch trip.
Recommended actions:
| Trips | Rectifier Set-up |
|---|---|
| Value | 94 |
| Short description | A rectifier has not been set-up correctly in a multi-power module system |
A rectifier has not been set-up correctly in a multi-power module system.
Recommended actions:
| Trips | Reserved 001 |
|---|---|
| Value | 1 |
| Short description | Reserved |
This trip value is used in Unidrive SP for an under voltage trip. The under voltage condition is now a drive state, and so this trip is no longer used by the drive.
| Trips | Reserved 105 |
|---|---|
| Value | 105 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 106 |
|---|---|
| Value | 106 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 107 |
|---|---|
| Value | 107 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 108 |
|---|---|
| Value | 108 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 165 |
|---|---|
| Value | 165 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 166 |
|---|---|
| Value | 166 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 168 |
|---|---|
| Value | 168 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 170 |
|---|---|
| Value | 170 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 171 |
|---|---|
| Value | 171 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 172 |
|---|---|
| Value | 172 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 173 |
|---|---|
| Value | 173 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 222 |
|---|---|
| Value | 222 |
| Short description | Reserved |
If this trip occurs please consult the drive supplier.
| Trips | Reserved 228 |
|---|---|
| Value | 228 |
| Short description | Reserved |
If this trip occurs please consult the drive supplier.
| Trips | Reserved 229 |
|---|---|
| Value | 229 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 230 |
|---|---|
| Value | 230 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 231 |
|---|---|
| Value | 231 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 232 |
|---|---|
| Value | 232 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 233 |
|---|---|
| Value | 233 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 234 |
|---|---|
| Value | 234 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 235 |
|---|---|
| Value | 235 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 236 |
|---|---|
| Value | 236 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 237 |
|---|---|
| Value | 237 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 238 |
|---|---|
| Value | 238 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 239 |
|---|---|
| Value | 239 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 240 |
|---|---|
| Value | 240 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 241 |
|---|---|
| Value | 241 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 242 |
|---|---|
| Value | 242 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 243 |
|---|---|
| Value | 243 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 244 |
|---|---|
| Value | 244 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 245 |
|---|---|
| Value | 245 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reserved 246 |
|---|---|
| Value | 246 |
| Short description | Reserved |
Reserved trip number.
| Trips | Reset |
|---|---|
| Value | 100 |
| Short description |
This is not a valid trip number as this value is used in User Trip (10.038) to reset the drive.
| Trips | Reset Logs |
|---|---|
| Value | 255 |
| Short description |
This is not a valid trip number as this value is used in User Trip (10.038) to reset the trip logs.
| Trips | Resistance |
|---|---|
| Value | 33 |
| Short description | Stator resistance measurement failed or value exceeds the allowed range |
This trip indicates that either the value being used for motor stator resistance is too high or that an attempt to do a test involving measuring motor stator resistance has failed. The maximum for the stator resistance parameters is generally higher than the maximum value that can be used in the control algorithms. If the value exceeds (VFS / sqrt(2)) / Full Scale Current Kc (11.061), where VFS is the full scale d.c. link voltage defined by VM_DC_VOLTAGE, then this trip is initiated. If the value is the result of a measurement made by the drive then sub-trip 1 is applied, or if it is because the parameter has been changed by the user then sub-trip 3 is applied. During the stator resistance section of auto-tuning an additional test is performed to measure the drive inverter characteristics to provide the compensation necessary for dead-times. If the inverter characteristic measurement fails then sub-trip 2 is applied.
| Sub-trip | Reason |
| 1 | Measured stator resistance exceeded the allowed range |
| 2 | It was not possible to measure the inverter characteristic |
| 3 | The stator resistance associated with either motor map exceeds the allowed range |
Recommended actions:
| Trips | Slot1 Different |
|---|---|
| Value | 204 |
| Short description | Option module in slot 1 has changed |
If the option module fitted in option slot 1 is different in any way to the option module present at the last power-down, then this trip is produced. Option modules can define the structure of their set-up and applications menus provided by the drive. This trip is initiated if a different module is fitted, but also if the structure of the menus provided by the option module has changed. The priority order for the option module different trips is Slot1 Different highest, then Slot2 Different, then Slot3 Different then Slot4 Different. The sub-trip indicates the reason for the trip as given below.
| Sub-trip | Reason | Defaults loaded |
| 1 | No module was fitted previously | Set-up and application menus |
| 2 | A module with the same identifier is fitted, but the set-up menu for this option slot has been changed. | Set-up menu |
| 3 | A module with the same identifier is fitted, but the applications menu for this option slot has been changed. | Applications menu |
| 4 | A module with the same identifier is fitted, but the set-up and applications menu for this option slot have been changed. | Set-up and application menus |
| >99 | Shows the identifier of the module previously fitted. | Set-up and application menus |
The trip can be reset and the module will operate correctly. If sub-trips 2 to 4 occur, then no further action is required and the trip will not occur on a subsequent power-up. If any other sub-trips occur a parameter save is required to prevent further trips on a subsequent power-up.
Recommended actions:
| Trips | Slot1 Error |
|---|---|
| Value | 202 |
| Short description | Option module in slot 1 has indicated an error |
The option module in option slot 1 has indicated an error. The option module can give the reason for the error and this is shown in the sub-trip number. As default the sub-trip number is shown as a number on the display, however, it is possible for the option module to supply sub-trip number strings which will be displayed instead of the number if available.
Recommended actions:
| Trips | Slot1 HF |
|---|---|
| Value | 200 |
| Short description | Fault with the option module in slot 1 that means that this module cannot operate |
This trip indicates that there is a fault with the option module in option slot 1 that means that this module cannot operate. The possible causes of the trip are given by the sub-trip value.
| Sub-trip | Reason |
| 1 | The module category cannot be identified. |
| 2 | The option module provides the structure of its set-up menu (Menu 15) and applications menu (Menu 25). It has not supplied the required information to the drive. |
| 3 | The option module requires memory space in the shared RAM between the drive and the option module to be able to pass communications messages to the drive. There is insufficient memory available to allocate the memory buffer for this module. |
| 4 | The option module has not indicated that it is running correctly during drive power-up sequence. |
| 5 | The option module has been removed after power-up or it has ceased to indicate to the drive processor that it is still active. |
| 6 | The drive has indicated that it is about to change mode (e.g. Open-loop to RFC-A). The option module has not stopped accessing drive user parameters and acknowledged this indication. |
| 7 | The drive has indicated that its processor is about to be reset. The option module has failed to acknowledge this indication. |
| 8 | The option module provides the structure of its set-up menu (Menu 15) and applications menu (Menu 25). An error has occurred during the download process. |
| 9 | The transfer of the set-up and applications menu structure information has taken more than 5s |
| 10 | The CRC in the set-up menu structure table or the applications menu structure provided by the option module is incorrect. |
Recommended actions:
| Trips | Slot1 Not Fitted |
|---|---|
| Value | 203 |
| Short description | Option module in slot 1 has been removed |
Each option module fitted in the drive is identified at power-up and the option fitted is stored by the drive in its non-volatile memory. If an option module was fitted in slot 1 at power-down, but that option module has subsequently been removed before power up then this trip is produced. The sub-trip number gives the identification code of the option module that has been removed. The priority order for the option module not fitted trips is Slot1 Not Fitted highest, then Slot2 Not Fitted, then Slot3 Not Fitted then Slot4 Not Fitted. If a drive user parameter save is not initiated before the drive power is removed and re-applied this trip will occur again after the next power-up. Until a drive user parameter save is performed it is possible to refit the module, which will then prevent the trip from occurring, and retain the parameter settings in the set-up menu (Menu 15) and applications menu (Menu 25). If a user parameter save is performed while this trip is active, the drive is powered down, the module refitted and the drive powered up, defaults settings will be loaded for these menus.
Recommended actions:
| Trips | Slot1 Watchdog |
|---|---|
| Value | 201 |
| Short description | Watchdog service error with the option module in slot 1 |
It is possible for some option modules to start a watchdog function in the drive. Once this has been done, the option module should service the watchdog regularly. This trip indicates that the watchdog has been started and then not service in time.
Recommended actions:
| Trips | Slot2 Different |
|---|---|
| Value | 209 |
| Short description | Option module in slot 2 has changed |
If the option module fitted in option slot 2 is different in any way to the option module present at the last power-down, then this trip is produced. Option modules can define the structure of their set-up and applications menus provided by the drive. This trip is initiated if a different module is fitted, but also if the structure of the menus provided by the option module has changed. The priority order for the option module different trips is Slot1 Different highest, then Slot2 Different, then Slot3 Different then Slot4 Different. The sub-trip indicates the reason for the trip as given below.
| Sub-trip | Reason | Defaults loaded |
| 1 | No module was fitted previously | Set-up and application menus |
| 2 | A module with the same identifier is fitted, but the set-up menu for this option slot has been changed. | Set-up menu |
| 3 | A module with the same identifier is fitted, but the applications menu for this option slot has been changed. | Applications menu |
| 4 | A module with the same identifier is fitted, but the set-up and applications menu for this option slot have been changed. | Set-up and application menus |
| >99 | Shows the identifier of the module previously fitted. | Set-up and application menus |
The trip can be reset and the module will operate correctly. If sub-trips 2 to 4 occur, then no further action is required and the trip will not occur on a subsequent power-up. If any other sub-trips occur a parameter save is required to prevent further trips on a subsequent power-up.
Recommended actions:
| Trips | Slot2 Error |
|---|---|
| Value | 207 |
| Short description | Option module in slot 2 has indicated an error |
The option module in option slot 2 has indicated an error. The option module can give the reason for the error and this is shown in the sub-trip number. As default the sub-trip number is shown as a number on the display, however, it is possible for the option module to supply sub-trip number strings which will be displayed instead of the number if available.
Recommended actions:
| Trips | Slot2 HF |
|---|---|
| Value | 205 |
| Short description | Fault with the option module in slot 2 that means that this module cannot operate |
This trip indicates that there is a fault with the option module in option slot 2 that means that this module cannot operate. The possible causes of the trip are given by the sub-trip value.
| Sub-trip | Reason |
| 1 | The module category cannot be identified. |
| 2 | The option module provides the structure of its set-up menu (Menu 16) and applications menu (Menu 26). It has not supplied the required information to the drive. |
| 3 | The option module requires memory space in the shared RAM between the drive and the option module to be able to pass communications messages to the drive. There is insufficient memory available to allocate the memory buffer for this module. |
| 4 | The option module has not indicated that it is running correctly during drive power-up sequence. |
| 5 | The option module has been removed after power-up or it has ceased to indicate to the drive processor that it is still active. |
| 6 | The drive has indicated that it is about to change mode (e.g. Open-loop to RFC-A). The option module has not stopped accessing drive user parameters and acknowledged this indication. |
| 7 | The drive has indicated that its processor is about to be reset. The option module has failed to acknowledge this indication. |
| 8 | The option module provides the structure of its set-up menu (Menu 16) and applications menu (Menu 26). An error has occurred during the download process. |
| 9 | The transfer of the set-up and applications menu structure information has taken more than 5s |
| 10 | The CRC in the set-up menu structure table or the applications menu structure provided by the option module is incorrect. |
Recommended actions:
| Trips | Slot2 Not Fitted |
|---|---|
| Value | 208 |
| Short description | Option module in slot 2 has been removed |
Each option module fitted in the drive is identified at power-up and the option fitted is stored by the drive in its non-volatile memory. If an option module was fitted in slot 2 at power-down, but that option module has subsequently been removed before power up then this trip is produced. The sub-trip number gives the identification code of the option module that has been removed. The priority order for the option module not fitted trips is Slot1 Not Fitted highest, then Slot2 Not Fitted, then Slot3 Not Fitted then Slot4 Not Fitted. If a drive user parameter save is not initiated before the drive power is removed and re-applied this trip will occur again after the next power-up. Until a drive user parameter save is performed it is possible to refit the module, which will then prevent the trip from occurring, and retain the parameter settings in the set-up menu (Menu 16) and applications menu (Menu 26). If a user parameter save is performed while this trip is active, the drive is powered down, the module refitted and the drive powered up, defaults settings will be loaded for these menus.
Recommended actions:
| Trips | Slot2 Watchdog |
|---|---|
| Value | 206 |
| Short description | Watchdog service error with the option module in slot 2 |
It is possible for some option modules to start a watchdog function in the drive. Once this has been done, the option module should service the watchdog regularly. This trip indicates that the watchdog has been started and then not service in time.
Recommended actions:
| Trips | Slot3 Different |
|---|---|
| Value | 214 |
| Short description | Option module in slot 3 has changed |
If the option module fitted in option slot 3 is different in any way to the option module present at the last power-down, then this trip is produced. Option modules can define the structure of their set-up and applications menus provided by the drive. This trip is initiated if a different module is fitted, but also if the structure of the menus provided by the option module has changed. The priority order for the option module different trips is Slot1 Different highest, then Slot2 Different, then Slot3 Different then Slot4 Different. The sub-trip indicates the reason for the trip as given below.
| Sub-trip | Reason | Defaults loaded |
| 1 | No module was fitted previously | Set-up and application menus |
| 2 | A module with the same identifier is fitted, but the set-up menu for this option slot has been changed. | Set-up menu |
| 3 | A module with the same identifier is fitted, but the applications menu for this option slot has been changed. | Applications menu |
| 4 | A module with the same identifier is fitted, but the set-up and applications menu for this option slot have been changed. | Set-up and application menus |
| >99 | Shows the identifier of the module previously fitted. | Set-up and application menus |
The trip can be reset and the module will operate correctly. If sub-trips 2 to 4 occur, then no further action is required and the trip will not occur on a subsequent power-up. If any other sub-trips occur a parameter save is required to prevent further trips on a subsequent power-up.
Recommended actions:
| Trips | Slot3 Error |
|---|---|
| Value | 212 |
| Short description | Option module in slot 3 has indicated an error |
The option module in option slot 3 has indicated an error. The option module can give the reason for the error and this is shown in the sub-trip number. As default the sub-trip number is shown as a number on the display, however, it is possible for the option module to supply sub-trip number strings which will be displayed instead of the number if available.
Recommended actions:
| Trips | Slot3 HF |
|---|---|
| Value | 210 |
| Short description | Fault with the option module in slot 3 that means that this module cannot operate |
This trip indicates that there is a fault with the option module in option slot 3 that means that this module cannot operate. The possible causes of the trip are given by the sub-trip value.
| Sub-trip | Reason |
| 1 | The module category cannot be identified. |
| 2 | The option module provides the structure of its set-up menu (Menu 17) and applications menu (Menu 27). It has not supplied the required information to the drive. |
| 3 | The option module requires memory space in the shared RAM between the drive and the option module to be able to pass communications messages to the drive. There is insufficient memory available to allocate the memory buffer for this module. |
| 4 | The option module has not indicated that it is running correctly during drive power-up sequence. |
| 5 | The option module has been removed after power-up or it has ceased to indicate to the drive processor that it is still active. |
| 6 | The drive has indicated that it is about to change mode (e.g. Open-loop to RFC-A). The option module has not stopped accessing drive user parameters and acknowledged this indication. |
| 7 | The drive has indicated that its processor is about to be reset. The option module has failed to acknowledge this indication. |
| 8 | The option module provides the structure of its set-up menu (Menu 17) and applications menu (Menu 27). An error has occurred during the download process. |
| 9 | The transfer of the set-up and applications menu structure information has taken more than 5s |
| 10 | The CRC in the set-up menu structure table or the applications menu structure provided by the option module is incorrect. |
Recommended actions:
| Trips | Slot3 Not Fitted |
|---|---|
| Value | 213 |
| Short description | Option module in slot 3 has been removed |
Each option module fitted in the drive is identified at power-up and the option fitted is stored by the drive in its non-volatile memory. If an option module was fitted in slot 3 at power-down, but that option module has subsequently been removed before power up then this trip is produced. The sub-trip number gives the identification code of the option module that has been removed. The priority order for the option module not fitted trips is Slot1 Not Fitted highest, then Slot2 Not Fitted, then Slot3 Not Fitted then Slot4 Not Fitted. If a drive user parameter save is not initiated before the drive power is removed and re-applied this trip will occur again after the next power-up. Until a drive user parameter save is performed it is possible to refit the module, which will then prevent the trip from occurring, and retain the parameter settings in the set-up menu (Menu 17) and applications menu (Menu 27). If a user parameter save is performed while this trip is active, the drive is powered down, the module refitted and the drive powered up, defaults settings will be loaded for these menus.
Recommended actions:
| Trips | Slot3 Watchdog |
|---|---|
| Value | 211 |
| Short description | Watchdog service error with the option module in slot 3 |
It is possible for some option modules to start a watchdog function in the drive. Once this has been done, the option module should service the watchdog regularly. This trip indicates that the watchdog has been started and then not service in time.
Recommended actions:
| Trips | Slot4 Different |
|---|---|
| Value | 254 |
| Short description | Option module in slot 4 has changed |
If the option module fitted in option slot 4 is different in any way to the option module present at the last power-down, then this trip is produced. Option modules can define the structure of their set-up and applications menus provided by the drive. This trip is initiated if a different module is fitted, but also if the structure of the menus provided by the option module has changed. The priority order for the option module different trips is Slot1 Different highest, then Slot2 Different, then Slot3 Different then Slot4 Different. The sub-trip indicates the reason for the trip as given below.
| Sub-trip | Reason | Defaults loaded |
| 1 | No module was fitted previously | Set-up and application menus |
| 2 | A module with the same identifier is fitted, but the set-up menu for this option slot has been changed. | Set-up menu |
| 3 | A module with the same identifier is fitted, but the applications menu for this option slot has been changed. | Applications menu |
| 4 | A module with the same identifier is fitted, but the set-up and applications menu for this option slot have been changed. | Set-up and application menus |
| >99 | Shows the identifier of the module previously fitted. | Set-up and application menus |
The trip can be reset and the module will operate correctly. If sub-trips 2 to 4 occur, then no further action is required and the trip will not occur on a subsequent power-up. If any other sub-trips occur a parameter save is required to prevent further trips on a subsequent power-up.
Recommended actions:
| Trips | Slot4 Error |
|---|---|
| Value | 252 |
| Short description | Option module in slot 4 has indicated an error |
The option module in option slot 4 has indicated an error. The option module can give the reason for the error and this is shown in the sub-trip number. As default the sub-trip number is shown as a number on the display, however, it is possible for the option module to supply sub-trip number strings which will be displayed instead of the number if available.
Recommended actions:
| Trips | Slot4 HF |
|---|---|
| Value | 250 |
| Short description | Fault with the option module in slot 4 that means that this module cannot operate |
This trip indicates that there is a fault with the option module in option slot 4 that means that this module cannot operate. The possible causes of the trip are given by the sub-trip value.
| Sub-trip | Reason |
| 1 | The module category cannot be identified. |
| 2 | The option module provides the structure of its set-up menu (Menu 24) and applications menu (Menu 28). It has not supplied the required information to the drive. |
| 3 | The option module requires memory space in the shared RAM between the drive and the option module to be able to pass communications messages to the drive. There is insufficient memory available to allocate the memory buffer for this module. |
| 4 | The option module has not indicated that it is running correctly during drive power-up sequence. |
| 5 | The option module has been removed after power-up or it has ceased to indicate to the drive processor that it is still active. |
| 6 | The drive has indicated that it is about to change mode (e.g. Open-loop to RFC-A). The option module has not stopped accessing drive user parameters and acknowledged this indication. |
| 7 | The drive has indicated that its processor is about to be reset. The option module has failed to acknowledge this indication. |
| 8 | The option module provides the structure of its set-up menu (Menu 24) and applications menu (Menu 28). An error has occurred during the download process. |
| 9 | The transfer of the set-up and applications menu structure information has taken more than 5s |
| 10 | The CRC in the set-up menu structure table or the applications menu structure provided by the option module is incorrect. |
Recommended actions:
| Trips | Slot4 Not Fitted |
|---|---|
| Value | 253 |
| Short description | Option module in slot 4 has been removed |
Each option module fitted in the drive is identified at power-up and the option fitted is stored by the drive in its non-volatile memory. If an option module was fitted in slot 4 at power-down, but that option module has subsequently been removed before power up then this trip is produced. The sub-trip number gives the identification code of the option module that has been removed. The priority order for the option module not fitted trips is Slot1 Not Fitted highest, then Slot2 Not Fitted, then Slot3 Not Fitted then Slot4 Not Fitted. If a drive user parameter save is not initiated before the drive power is removed and re-applied this trip will occur again after the next power-up. Until a drive user parameter save is performed it is possible to refit the module, which will then prevent the trip from occurring, and retain the parameter settings in the set-up menu (Menu 24) and applications menu (Menu 28). If a user parameter save is performed while this trip is active, the drive is powered down, the module refitted and the drive powered up, defaults settings will be loaded for these menus.
Recommended actions:
| Trips | Slot4 Watchdog |
|---|---|
| Value | 251 |
| Short description | Watchdog service error with the option module in slot 4 |
It is possible for some option modules to start a watchdog function in the drive. Once this has been done, the option module should service the watchdog regularly. This trip indicates that the watchdog has been started and then not service in time.
Recommended actions:
| Trips | Slot App Menu |
|---|---|
| Value | 216 |
| Short description | Application menu customisation conflict error |
This trip indicates that more than one option slot has requested to customize application menus 18, 19 and 20. The sub-trip number indicates which option slot has been allowed to customize the menus.
Recommended actions:
| Trips | Soft Start |
|---|---|
| Value | 226 |
| Short description | Soft start relay failed to close or soft start relay monitoring failed |
This trip indicates that the soft start relay in the drive has failed to close or the soft start monitoring circuit has failed.
Recommended actions:
Note: This trip does not exist in firmware V01.58.00.00 and later.
| Trips | Stored HF |
|---|---|
| Value | 221 |
| Short description | Hardware trip occurred prior to last power down |
If an HFxx trip occurs then a Stored HF trip occurs each time the drive is powered up until this trip is reset. The sub-trip code is the number of the original HF trip. The Stored HF trip can be reset by first writing 1299 to Pr mm.000 and resetting the drive. The drive should then be power cycled. This trip is also reset if bootable files are present on a media card fitted in the drive at power-up which include a drive user program as File 002.
Recommended actions:
| Trips | Sub-array RAM |
|---|---|
| Value | 227 |
| Short description | RAM allocation error |
An option module, derivative image or user program image has requested more parameter RAM than is allowed. The RAM allocation is checked in order of resulting sub-trip numbers, and so the failure with the highest sub-trip number is given. The sub-trip is calculated as (parameter size x 1000) + (parameter type x 100) + sub-array number. Note that if this trip occurs, all menu customisation provided by option modules, the derivative image or the user program image is not used. The tables below show the values corresponding to the parts of the sub-trip number.
| Parameter size | Value |
| 1 bit | 1 |
| 8 bit | 2 |
| 16 bit | 3 |
| 32 bit | 4 |
| 64 bit | 5 |
| Parameter type | Value |
| Volatile | 0 |
| User save | 1 |
| Power-down save | 2 |
| Sub-array | Menus | Value |
| Applications menus | 18-20 | 1 |
| Derivative image | 29 | 2 |
| User program image | 30 | 3 |
| Option slot 1 set-up | 15 | 4 |
| Option slot 1 applications | 25 | 5 |
| Option slot 2 set-up | 16 | 6 |
| Option slot 2 applications | 26 | 7 |
| Option slot 3 set-up | 17 | 8 |
| Option slot 3 applications | 27 | 9 |
| Option slot 4 set-up | 24 | 10 |
| Option slot 4 applications | 28 | 11 |
| Trips | Temp Feedback |
|---|---|
| Value | 218 |
| Short description | Fault with a thermistor in the drive |
This trip indicates a fault with a thermistor in the drive (i.e. open circuit or short circuit).
| Source | xx | y | zz |
| Control board |
00 | 00 | 01: Control board thermistor 1 02: Control board thermistor 2 03: I/O board thermistor |
| Power system | Power module number | 0 | Zero for temperature feedback provided via power system comms. 21, 22 and 23 for direct ELV temperature feedback. |
| Power system | 01 | Rectifier number* | Always zero |
*For a parallel power-module system the rectifier number will be one as it is not possible to determine which rectifier has detected the fault.
Recommended actions:
| Trips | Th Brake Res |
|---|---|
| Value | 10 |
| Short description | Brake resistor over temperature |
If hardware based braking resistor thermal monitoring is provided and the resistor overheats this trip is initiated. If the braking resistor is not present then this trip must be disabled with bit 3 of Action On Trip Detection (10.037) to prevent this trip.
Recommended actions:
| Trips | Th Short Circuit |
|---|---|
| Value | 25 |
| Short description | Motor thermistor short circuit |
This trip indicates that a temperature sensor connected to an analog input or terminal 15 on the position feedback interface (where applicable) has a low impedance (i.e. < 50 ohms). The cause of the trip can be identified by the sub-trip number.
| Sub-trip | Reason | Recommended actions |
| 1 | Analog input 1 | Check temperature feedback connection and cabling to analog input 1. Replace sensor. Check that the setting of Analog Input 1 Mode (07.007) is correct. |
| 2 | Analog input 2 | Check temperature feedback connection and cabling to analog input 2. Replace sensor. Check that the setting of Analog Input 2 Mode (07.011) is correct. |
| 3 | Analog input 3 | Check temperature feedback connection and cabling to analog input 3. Replace sensor. Check that the setting of Analog Input 3 Mode (07.015) is correct. |
| 4 | Position feedback interface | Check temperature feedback connection and cabling to pin 15 of the position feedback interface. Replace sensor. Check that the setting of P1 Thermistor Fault Detection (03.123) is correct. |
| Trips | Thermistor |
|---|---|
| Value | 24 |
| Short description | Motor thermistor over temperature |
This trip indicates that a temperature sensor connected to one of the analog inputs or terminal 15 on the position feedback interface (15-way D-type connector) (where applicable) has indicated an over-temperature. The source of the trip can be identified by the sub-trip number.
| Sub-trip | Reason | Recommended actions |
| 1 | Analog input 1 | Check why the temperature measured by the sensor connected analog input 1 is too high. Check temperature sensor connection. Check that the setting of Analog Input 1 Mode (07.007) is correct |
| 2 | Analog input 2 | Check why the temperature measured by the sensor connected analog input 2 is too high. Check temperature sensor connection. Check that the setting of Analog Input 2 Mode (07.011) is correct |
| 3 | Analog input 3 | Check why the temperature measured by the sensor connected analog input 3 is too high. Check temperature sensor connection. Check that the setting of Analog Input 3 Mode (07.015) is correct |
| 4 | Position feedback interface | Check why the temperature measured by the sensor connected to pin 15 of the position feedback interface is too high. Check temperature sensor connection. Check that the setting of P1 Thermistor Fault Detection (03.123) is correct |
| Trips | Undefined |
|---|---|
| Value | 110 |
| Short description | Power system indicated a trip but did not identify the reason |
In a standard drive this trip indicates that the power system has generated but did not identify the trip from the power system. The cause of the trip is unknown.
In a 4 quadrant drive this indicates that the input converter control system has initated a trip which is not included in the normal trip system. The sub-trip number indicates the reason for the trip. The value given corresonds to the values in Trip 0 (10.020).
| Trips | User 24V |
|---|---|
| Value | 91 |
| Short description | User 24V supply not present on control terminals when required |
This trip is initiated if User Supply Select (06.072) = 1 or Low Under Voltage Threshold Select (06.067) = 1 or Backup Supply Mode Enable (06.068) = 1 and no user 24V present on the user 24V input. (Note that if an active input rectifier is present this trip could be produced with a sub-trip of 100. This simply indicates that the same error condition has been detected by the active input converter first.)
Recommended actions:
| Trips | User Prog Trip |
|---|---|
| Value | 96 |
| Short description | Trip generated by an onboard user program |
This trip can be initiated from within an onboard user program using a function call which defines the sub-trip number.
Recommended actions:
| Trips | User Program |
|---|---|
| Value | 249 |
| Short description | Onboard user program error |
An error has been detected in the onboard user program image. The sub-trip indicated the reason for the trip.
| Sub-trip | Reason | Comments |
| 1 | Divide by zero | |
| 2 | Undefined trip | |
| 3 | Attempted fast parameter access set-up with non-existent parameter | |
| 4 | Attempted access to non-existent parameter | |
| 5 | Attempted write to read-only parameter | |
| 6 | Attempted an over-range write | |
| 7 | Attempted read from write-only parameter | |
| 30 | The image has failed because either its CRC is incorrect, or there are less than 6 bytes in the image or the image header version is less than 5. | Occurs when the drive powers-up or the image is programmed. The image tasks will not run. |
| 31 | The image requires more RAM for heap and stack than can be provided by the drive. | As 30. |
| 32 | The image requires an OS function call that is higher than the maximum allowed. | As 30. |
| 33 | The ID code within the image is not valid | As 30. |
| 40 | The timed task has not completed in time and has been suspended. | The user program enable bit is reset to zero when the trip is initiated. |
| 41 | Undefined function called, i.e. a function in the host system vector table that has not been assigned. | As 40. |
| 52 | Customisable menu table CRC check failed | As 30. |
| 53 | Customisable menu table changed | Occurs when the drive powers-up or the image is programmed and the table has changed. Defaults are loaded for the user program menu and the trip will keep occurring until drive parameters are saved. |
| 80 | *Image is not compatible with the control board | Initiated from within the image code. |
| 81 | *Image is not compatible with the control board serial number | As 80. |
| 100 | Image has detected and prevented attempted pointer access outside of the IEC task's heap area. | |
| 101 | Image has detected and prevented misaligned pointer usage. | |
| 102 | Image has detected an array bounds violation and prevented its access. | |
| 103 | Image has attempted to convert a data type to or from an unknown data type, has failed and has shut itself down. | |
| 104 | Image has attempted to use an unknown user service function. | |
| 200 | User program has invoked a "divide" service with a denominator of zero. (Note that this is raised by the downloaded image and has therefore been given a distinct error code despite being the same fundamental problem as sub-trip 1.) | |
| 201 | Parameter access is not supported. An attempt to read database other than the host drive. | |
| 202 | Parameter does not exist. Database was host drive but the specified parameter does not exist. | |
| 203 | Parameter is read-only. | |
| 204 | Parameter is write-only. | |
| 205 | Unknown parameter error. | |
| 206 | Invalid bit present in parameter. The parameter does not contain the specified bit. | |
| 207 | Parameter format lookup failed. Failed to get parameter information data. | |
| 208 | An over-range write has been attempted. |
The following table gives the differences when compared to the derivative product image.
| Sub-trip | Difference |
| 40, 41 | The user program enable bit is reset to zero when the trip is initiated. |
| 51 | Not applicable as core menu customisation not allowed |
| 6x | Not applicable as option module restrictions not allowed |
| 7x | Not applicable as option module restrictions not allowed |
| 100 | Image has detected and prevented attempted pointer access outside of the IEC task's heap area. |
| 101 | Image has detected and prevented misaligned pointer usage. |
| 102 | Image has detected an array bounds violation and prevented its access. |
| 103 | Image has attempted to convert a data type to or from an unknown data type, has failed and has shut itself down. |
| 104 | Image has attempted to use an unknown user service function. |
| 200 | User program has invoked a "divide" service with a denominator of zero. (Note that this is raised by the downloaded image and has therefore been given a distinct error code despite being the same fundamental problem as sub-trip 1.) |
o
t applicable| Trips | User Save |
|---|---|
| Value | 36 |
| Short description | Error detected in the user save parameter data saved in non-volatile memory |
This trip indicates that an error has been detected in the user save parameters saved in non-volatile memory. For example, following a user save command, if the power to the drive was removed when the user parameters were being saved.
Recommended actions:
| Trips | User Trip 40 |
|---|---|
| Value | 40 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 41 |
|---|---|
| Value | 41 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 42 |
|---|---|
| Value | 42 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 43 |
|---|---|
| Value | 43 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 44 |
|---|---|
| Value | 44 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 45 |
|---|---|
| Value | 45 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 46 |
|---|---|
| Value | 46 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 47 |
|---|---|
| Value | 47 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 48 |
|---|---|
| Value | 48 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 49 |
|---|---|
| Value | 49 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 50 |
|---|---|
| Value | 50 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 51 |
|---|---|
| Value | 51 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 52 |
|---|---|
| Value | 52 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 53 |
|---|---|
| Value | 53 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 54 |
|---|---|
| Value | 54 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 55 |
|---|---|
| Value | 55 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 56 |
|---|---|
| Value | 56 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 57 |
|---|---|
| Value | 57 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 58 |
|---|---|
| Value | 58 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 59 |
|---|---|
| Value | 59 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 60 |
|---|---|
| Value | 60 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 61 |
|---|---|
| Value | 61 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 62 |
|---|---|
| Value | 62 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 63 |
|---|---|
| Value | 63 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 64 |
|---|---|
| Value | 64 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 65 |
|---|---|
| Value | 65 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 66 |
|---|---|
| Value | 66 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 67 |
|---|---|
| Value | 67 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 68 |
|---|---|
| Value | 68 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 69 |
|---|---|
| Value | 69 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 70 |
|---|---|
| Value | 70 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 71 |
|---|---|
| Value | 71 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 72 |
|---|---|
| Value | 72 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 73 |
|---|---|
| Value | 73 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 74 |
|---|---|
| Value | 74 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 75 |
|---|---|
| Value | 75 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 76 |
|---|---|
| Value | 76 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 77 |
|---|---|
| Value | 77 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 78 |
|---|---|
| Value | 78 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 79 |
|---|---|
| Value | 79 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 80 |
|---|---|
| Value | 80 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 81 |
|---|---|
| Value | 81 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 82 |
|---|---|
| Value | 82 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 83 |
|---|---|
| Value | 83 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 84 |
|---|---|
| Value | 84 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 85 |
|---|---|
| Value | 85 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 86 |
|---|---|
| Value | 86 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 87 |
|---|---|
| Value | 87 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 88 |
|---|---|
| Value | 88 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 89 |
|---|---|
| Value | 89 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 127 |
|---|---|
| Value | 127 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 128 |
|---|---|
| Value | 128 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 129 |
|---|---|
| Value | 129 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 130 |
|---|---|
| Value | 130 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 131 |
|---|---|
| Value | 131 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 132 |
|---|---|
| Value | 132 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 133 |
|---|---|
| Value | 133 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 134 |
|---|---|
| Value | 134 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 135 |
|---|---|
| Value | 135 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 136 |
|---|---|
| Value | 136 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 137 |
|---|---|
| Value | 137 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 138 |
|---|---|
| Value | 138 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 139 |
|---|---|
| Value | 139 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 140 |
|---|---|
| Value | 140 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 141 |
|---|---|
| Value | 141 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 142 |
|---|---|
| Value | 142 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 143 |
|---|---|
| Value | 143 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 144 |
|---|---|
| Value | 144 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 145 |
|---|---|
| Value | 145 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 146 |
|---|---|
| Value | 146 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 147 |
|---|---|
| Value | 147 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 148 |
|---|---|
| Value | 148 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 149 |
|---|---|
| Value | 149 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 150 |
|---|---|
| Value | 150 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 151 |
|---|---|
| Value | 151 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 152 |
|---|---|
| Value | 152 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 153 |
|---|---|
| Value | 153 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 154 |
|---|---|
| Value | 154 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 155 |
|---|---|
| Value | 155 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 156 |
|---|---|
| Value | 156 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 157 |
|---|---|
| Value | 157 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 158 |
|---|---|
| Value | 158 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | User Trip 159 |
|---|---|
| Value | 159 |
| Short description | User generated trip |
This trip is not used by the drive and can be used for a user trip.
| Trips | Voltage Range |
|---|---|
| Value | 169 |
| Short description | Supply voltage is outside of the defined range in Regen mode |
Not Applicable
| Trips | Watchdog |
|---|---|
| Value | 30 |
| Short description | Control word watchdog has timed out |
This trip indicates that a watchdog within the drive has been enabled and has timed out as given in the table below.
| Sub-trip | Reason |
| No sub-trip | The Control word watchdog ( Control Word (06.042) Bit 14) has timed out. |
| 1 | An application is running in a PC application that is controlling the drive and using an internal watchdog for comms loss detection. The comms connection has been lost and the watchdog has timed out. |